ci: declare empty permissions on release workflow#1491
Open
arpitjain099 wants to merge 1 commit into
Open
Conversation
The release job clones with DENOBOT_PAT and runs the publish-release
task with the same PAT for GITHUB_TOKEN. The workflow's own GITHUB_TOKEN
is unused. permissions:{} captures that.
Style matches the per-job permission block in ci.yml.
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins the release job to
permissions: {}. The job checks out the repo withsecrets.DENOBOT_PATand runsdeno run -A jsr:@deno/rust-automation@0.22.0/tasks/publish-releasewithGITHUB_TOKEN: ${{ secrets.DENOBOT_PAT }}. The workflow's ownGITHUB_TOKENis never used.Defense-in-depth angle: a compromised third-party action (cf. CVE-2025-30066) runs inside the existing job context and exfiltrates whatever scope the workflow token holds via build logs. With
permissions: {}the token has zero scope to leak; release authority lives only inDENOBOT_PAT.Matches the per-job permission block already declared in
ci.yml. YAML validated locally withyaml.safe_load.